-
-
Notifications
You must be signed in to change notification settings - Fork 33
feat: use getAsFileSystemHandle when available #91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@tomayac please check this PR out. I've added some tests and additional typescript type support for the new |
Pull Request Test Coverage Report for Build ae387457db4eb1e92b2d2a815de8bc263fd43dd2-PR-91Details
💛 - Coveralls |
254b192 to
cc7ca27
Compare
tomayac
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I'm not sure if it matters, but you may want to replace FileSystemHandle with the more explicit FileSystemFileHandle, since this is only dealing with files, not directories (for which FileSystemDirectoryHandle exists, both inherit from FileSystemHandle).
src/file-selector.spec.ts
Outdated
| const name = 'test.json'; | ||
| const [f, h] = createFileSystemFileHandle(name, {ping: true}, { | ||
| type: 'application/json' | ||
| }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| }) | |
| }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed this.
cc7ca27 to
702d098
Compare
Made the |
|
@tomayac can we go ahead with this PR or would you like to update yours to match this one? |
No worries with taking yous. Just close mine in favor of this. Glad the feature is landing. |
|
🎉 This PR is included in version 1.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
What kind of change does this PR introduce?
Did you add tests for your changes?
If relevant, did you update the documentation?
Summary
Complete the impl. of #79 with tests and typescript types.
Does this PR introduce a breaking change?
No.
Other information